Apparatus for managing folder and method for the same

ABSTRACT

An apparatus for managing a folder, includes: a memory; and a processor electrically connected to the memory. The processor is configured to detect access of a user terminal, provide a folder list for folders or a file list for files in a folder, and when an access authority of the user terminal to a specific folder is confirmed, provide a folder memo pad including a folder memo in a process of providing a folder list and a folder badge associated with the specific folder, wherein the folder memo is realized as a memo pad associated with the specific folder in the user terminal and for which modification is tracked.

CROSS-REFERENCE TO PRIOR APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/841,170 (filed on Jun. 15, 2022), which is a continuation of U.S.patent application Ser. No. 16/209,390 (filed on Dec. 4, 2018 and issuedas U.S. Pat. No. 11,392,548 on Jul. 19, 2022), which claims priority toKorean Patent Application Nos. 10-2017-0165758 (filed on Dec. 5, 2017),10-2018-0002417 (filed on Jan. 8, 2018), 10-2018-0005033 (filed on Jan.15, 2018), 10-2018-0124610 (filed on Oct. 18, 2018), 10-2018-0124625(filed on Oct. 18, 2018), and 10-2018-0133210 (filed on Nov. 2, 2018),which are all hereby incorporate by reference in their entirety.

BACKGROUND

The present invention relates to a folder management technique, and morespecifically, to a technique for providing a notification to a userusing a badge.

A folder sharing technique implements folders which can be used by twoor more users and can provide a function of uploading or downloadingfiles requested by two or more users. As the number of users who usefolder sharing programs increases, a variety of file sharingapplications for efficiently providing folder sharing processes betweenvarious users are developed.

SUMMARY

The present invention relates to a folder management apparatus andmethod for intuitively notifying a user of a shared folder and uncheckeddetails accumulated in the shared folder, thereby improving userconvenience.

An embodiment of the present invention provides a folder managementapparatus and method capable of intuitively notifying a user of folderupdate made by other users by managing shared folders and files in theshared folders using the concepts of a folder badge per user per folderand a file badge per user per file, thereby improving user convenience.

According to one embodiment of the present invention, there is provideda folder management apparatus including a memory and a processorelectrically connected to the memory, wherein the processor isconfigured to detect access of a user terminal and to display at leastone folder permitted to be accessed by the user terminal along with afolder badge corresponding to the folder, wherein, when update historiesincluding modification and new generation with respect to the folderpermitted to be accessed by the user terminal are generated, the folderbadge indicates the number of update histories which have not been yetread by the user terminal among the update histories.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a folder management system according toan embodiment of the present invention.

FIG. 2 is a block diagram showing a folder management apparatusaccording to an embodiment of the present invention.

FIG. 3 is a block diagram showing functional elements of a processorincluded in the folder management apparatus according to an embodimentof the present invention.

FIG. 4 is a block diagram showing a file badge manager of the processorin the folder management apparatus according to an embodiment of thepresent invention.

FIG. 5 is a diagram showing a folder list, files in folders and a listof subfolders along with badges according to an embodiment of thepresent invention.

FIG. 6 is a diagram illustrating an embodiment of a procedure in which afolder badge manager of the present invention manages folder updatehistory using a sequential list vectorized in time series.

FIG. 7 is a flowchart showing a folder management method according to anembodiment of the present invention.

FIG. 8 is a flowchart showing a folder management method according toanother embodiment of the present invention.

DETAILED DESCRIPTION

Description of the present invention is merely an embodiment forstructural or functional explanation and thus the scope of the presentinvention should not be interpreted as being limited by embodimentsdescribed in the specification. That is, embodiments can be modified invarious manners and have various forms and thus the scope of the presentinvention should be understood to include equivalents that can realizethe technical ideas. In addition, the objectives and effects proposed inthe present invention are not intended to be included in a specificembodiment or only the effects are not intended to be included thereinand thus the scope of the present invention should not be understood tobe limited thereby.

Meanwhile, the terms used in the present application should beunderstood as follows.

Terms such as “first” and “second” are used to distinguish one componentfrom another component and the scope of the present invention is notlimited by such terms. For example, a first element may be called asecond element and the second element may be called the first element.

When an element is “coupled” or “connected” to another element, itshould be understood that a third element may be present between the twoelements although the element may be directly coupled or connected tothe other element. When an element is “directly coupled” or “directlyconnected” to another element, it should be understood that no elementis present between the two elements. Further, other expressions fordescribing a relationship between elements, that is, “between”,“directly between”, “adjacent to”, “directly adjacent to” and the likeshould be interpreted in the same manner.

An element described in the singular form is intended to include aplurality of elements unless the context clearly indicates otherwise. Inaddition, in the specification of the present invention, it will befurther understood that the terms “comprise” and “include” specify thepresence of stated features, integers, steps, operations, elements,components, and/or combinations thereof, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or combinations.

In the method invention, steps may be performed in different order fromthe described order unless the context clearly indicates otherwise. Thatis, steps may be performed in the same order as the described one,performed substantially simultaneously or performed in reverse order.

The present invention can be implemented with computer-readable code ina computer-readable recording medium, and the computer-readablerecording medium may include all kinds of recording devices capable ofstoring data readable by a computer system. Examples of thecomputer-readable medium may include a ROM, a RAM, a CD-ROM, magnetictapes, floppy disks, optical data storage devices, and the like.Further, the computer-readable recording medium is distributed to acomputer system connected via a network and computer-readable code canbe saved and executed according to a distributed system.

It is to be noted that most terms disclosed in the present inventioncorrespond to general terms well known in the art. Terms defined ingenerally used dictionaries should be interpreted as being consistentwith contextual meanings of related art and cannot be interpreted ashaving ideal or excessively formal meanings unless clearly defined inthe present application.

FIG. 1 is a diagram illustrating a folder management system according toan embodiment of the present invention.

Referring to FIG. 1 , a folder management system 100 includes a foldermanagement apparatus 110 and one or more user terminals 120.

The folder management apparatus 110 corresponds to a computing devicewhich can be connected to at least one user terminal 120 through anetwork. In an embodiment, the folder management apparatus 110 maymanage at least one member group in which a user associated with theuser terminal 120 is included as a member.

In an embodiment, the folder management apparatus 110 may be connectedto the user terminal 120 through a shared folder agent installed in theuser terminal 120. Here, the shared folder agent corresponds to an agentprogram which is software capable of allowing the user terminal 120 andthe folder management apparatus 110 to inter-operate with the permissionof the user terminal 120 when installed in the user terminal 120.

The user terminal 120 corresponds to a computing device connectable tothe folder management apparatus 110 through a network, for example, adesktop computer, a notebook computer, a tablet PC, a smartphone or thelike.

In an embodiment, a first user terminal 120 a may correspond to a mobileterminal and may be connected to the folder management apparatus 110through cellular communication or Wi-Fi communication. In anotherembodiment, a second user terminal 120 b may correspond to a desktopcomputer and may be connected to the folder management apparatus 110through the Internet.

FIG. 2 is a block diagram showing the folder management apparatusaccording to an embodiment of the present invention.

Referring to FIG. 2 , the folder management apparatus 110 may include aprocessor 210, a memory 220, a user input/output unit 230 and a networkinput/output unit 240.

The processor 210 can execute a shared folder management processaccording to an embodiment of the present invention, manage the memory220 for which writing or reading is performed in the process andschedule synchronization time between a volatile memory and anonvolatile memory in the memory 220.

The processor 210 can control the overall operation of the foldermanagement apparatus 110 and can be electrically connected to the memory220, the user input/output unit 230 and the network input/output unit240 to control data flow therebetween. The processor 210 may be realizedby a central processing unit (CPU) of the folder management apparatus110.

The memory 220 may include an auxiliary storage device which isimplemented by a nonvolatile memory such as a solid state disk (SSD) ora hard disk drive (HDD) and used to store data necessary for the foldermanagement apparatus 110 and a main storage device implemented by avolatile memory such as a random access memory (RAM). In this manner,the memory 220 can be implemented by a volatile memory and a nonvolatilememory. If the memory 220 is implemented by a nonvolatile memory, thememory 220 can be implemented to be connected through a hyperlink.

The user input/output unit 230 may provide an environment for receivinguser input and an environment for outputting specific information to auser and include an input device including an adaptor such as a mouse, atrackball, a touchpad, a graphic tablet, a scanner, a touchscreen, akeyboard or a pointing device and an output device including an adaptorsuch as a monitor or a touchscreen. In an embodiment, the userinput/output unit 230 may correspond to a computing device connectedthrough remote access. In such a case, the folder management apparatus110 can serve as a server.

The network input/output unit 240 may provide an environment forconnecting to the user terminal 120 through a network and include anadaptor for local area network (LAN) communication, for example.

FIG. 3 is a block diagram showing functional elements of the processorincluded in the folder management apparatus according to an embodimentof the present invention.

Referring to FIG. 3 , the processor 210 may include a folder accessmanager 310, a folder list provider 320, a file list provider 330, afolder badge manager 340, a file badge manager 350, an updatenotification unit 360 and a controller 370.

However, the processor 210 according to an embodiment of the presentinvention does not necessarily include all of the aforementionedcomponents simultaneously and some of the components may be omitted orsome or all of the component may be selectively included in theprocessor 210 according to embodiments.

When the user terminal 120 accesses or intends to access a foldermanagement system or a folder, the folder access manager 310 receives arequest of access of the user terminal 120. More specifically, thefolder access manager 310 can receive a request of access to the foldermanagement system or a specific folder from the user terminal 120, checkthe access authority of the corresponding user and determine whether topermit the access.

Here, the folder access manager 310 can check the authority of the userterminal 120 to access a folder by acquiring user information associatedwith the user terminal 120 or identification information of the userterminal. The folder access manager 310 can permit access only when itis confirmed that the corresponding user or corresponding user terminalhas the authority to access the folder management system or the folder.

In an embodiment, presence or absence of the authority to access afolder may be determined through user invitation performed by a foldergenerator when the folder is generated. That is, only a user invited bythe folder generator to the corresponding folder has the authority toaccess the folder.

The folder access manager 310 can perform management such as adding,modifying or deleting a file or a subfolder with respect to a folder onthe basis of a request of a folder user. Here, a file may include textfiles transmitted from the user terminal 120 or general user files suchas a multimedia file.

The folder list provider 320 provides a folder list only when the folderaccess manager 310 confirms that the corresponding user terminal 120 hasthe access authority. Here, folders in a provided list may be limited tofolders confirmed to be accessible by the corresponding user terminal120. Further, the folder list provider 320 may provide a folder badgecorresponding each folder along with the folder list.

The folder list provider 320 may include a folder manager (not shown).The folder manager can generate and manage folders. More specifically,the folder manager can generate a folder on the basis of a user request,generate a subfolder in the folder and manage the subfolder.

In an embodiment, the folder manager can generate a specific folderdesignated with a folder generator by a user associated with thecorresponding user terminal 120 when a folder generation request isreceived from the user terminal 120. In addition, the folder manager caninvite folder sharers according to designation of the folder generatorand determine at least one folder sharer participating in thecorresponding folder.

In an embodiment, when a folder is generated by a folder generator, thefolder manager can assign access authority of the folder generatorincluding folder deletion authority to the folder generator and assignaccess authority of a folder sharer from which the folder deletionauthority has been excluded to each folder participant.

The file list provider 330 can provide a list of files in a specificfolder when the user terminal 120 accesses and opens the specificfolder. Here, a file list can be provided with respect to only files forwhich the user terminal 120 has the access or reading authority. Inaddition, the file list provider 330 can provide a file badge per userper file to each user along with the file list.

Here, a file can include all types of objects such as text, stillimages, moving images, tables and audio data stored in folders oraccessible through folders. Further, a file can include a folder memoassociated with a corresponding folder, a task object stored in acorresponding folder, accessible through the folder or associated with afile in the folder, a file associated with a task object, and the like.

Particularly, a file badge with respect to a folder memo pad may bedesignated as a file badge or a folder memo badge. Similarly, a filebadge with respect to a folder chat room may be designated as a filebadge or a folder chat room badge and a file badge with respect to atask object may be designated as a file badge or a task object badge.

In addition, when a task object, a folder memo pad and a folder chatroom are associated with a file, update histories generated in the taskobject, the folder memo pad and the folder chat room may also bereflected in the file badge of the file associated therewith and thefolder badge of a folder associated therewith.

In an embodiment, the folder list provider 320 can provide a list ofsubfolders in a specific folder and metadata about the subfolders whenthe user terminal 120 is permitted to access the specific folder throughthe folder access manager 310 and also provide subfolder badgescorresponding to the subfolders. In addition, the file list provider 330can provide metadata about a file in the folder and a file listincluding an access path to the file to the user terminal 120 permittedto access the folder by the folder access manager 310 and the folderlist provider 320.

More specifically, when the user terminal 120 is permitted to access afolder by the folder access manager 310, the folder list provider 320can provide i) metadata about subfolders in the folder and ii) a folderbadge per user per folder including information about modificationperformed by each folder user participating in the folder with respectto each subfolder in the folder to the user terminal 120.

In addition, when the user terminal 120 is permitted to access aspecific folder by the folder access manager 310, the folder listprovider 320 can provide i) a file list including metadata about a filein the folder and ii) a file badge per user per file includinginformation about modifications performed by each folder userparticipating in the folder with respect to each file in the folder andhaving the authority to modify the file to the user terminal 120.

The folder badge manager 340 generates, computes and updates folderbadges using folder update histories and user access information. Here,a folder may include a subfolder. In addition, the file badge manager350 generates, computes and updates file badges using update historiesof files in folders and user access information. In addition, a filebadge value can be added to a folder badge value of a folder to whichthe corresponding file belongs.

A folder badge represents update histories with respect a specificfolder. The update histories include new generation or changes insettings and modification of the specific folder, upload and/ormodification of a file in the specific folder, addition and change of afile in the specific folder, new generation or changes in settings of asubfolder in the specific folder, and update histories generated withrespect to a file in the subfolder. However, a folder badge valueaccording to an embodiment of the present invention represents only thenumber of accumulated update histories which are not checked by aspecific user instead of the number of all accumulated update historiesdue to the aforementioned events.

A file badge represents the number of unchecked update histories whichhave not been yet read or checked by a user among the number ofaccumulated update histories with respect to a specific file when theupdate histories are generated. The update histories include events suchas upload and/or modification, addition, change and update of thespecific file. That is, in an embodiment of the present invention, afolder badge or a file badge can represent the number of uncheckedupdate histories of a specific user among update events i included inthe update histories with respect to the specific user.

Accordingly, folder badges are recorded per folder and counted, recordedand visualized per user. This is because, when a plurality of usersparticipates in folder sharing, folders which have been open or have notbeen open by the users, files which have been read or have not been readby the users and update histories of folders and files are different.Accordingly, a folder badge may be an index which quantifies andindicates details required to be read and checked later by a specificuser with respect to a specific folder.

For example, a folder badge per user per folder may be described asfollows. If a folder management system includes folder 1 and folder 2and folder users A and B, modification and update information aboutfolder 1 and folder 2 and read information about folder 1 and folder 2of each of user A and user B can be represented.

That is, when folder 1 is newly generated as a folder accessible by userA, a folder badge value of folder 1 is 1. When new file 1-1 is generatedin folder 1, the folder badge value of folder 1 becomes 2. When user Aaccesses and reads uploaded folder 1, the folder badge value of folder 1becomes 0.

Thereafter, when user B or user C, who are each an authorized user,performs a folder update operation such as modification, change and fileor memo addition on folder 1 and thus n folder update histories aregenerated, the file badge value of folder 1 visualized to user A beforeuser A checks the update histories is n. When user A checks all the nfolder update histories by opening folder 1 and reading generated ormodified folders or files, the folder badge value of folder 1 visualizedto user A changes to 0.

The folder badge manager 340 can detect folder or file modificationsperformed by an arbitrary user terminal 120 and update auser-independent folder modification history per file. Here, theuser-independent folder modification history per file includes foldermodification results of users with respect to each folder.

Here, update of a folder can include not only modifications and changesin settings of the folder but also update histories generated insubfolders included in the folder and update histories generated infiles included in the folder.

Update of a folder can refer to direct modifications or changes ofsettings or a state of the folder, such as change of the folder name,change of a folder participant and change of the authority of a folderparticipant, rather than folder update due to update of a file or asubfolder included in the folder.

When an update history is generated in a file included in a folder, theupdate history needs to be checked by a folder participant and thusgeneration of an unchecked update history with respect to a file isreflected in a folder badge value. A case in which a file has been newlygenerated, modified, changed or edited and a case in which the authorityto access a file has been changed may be examples of an update historygenerated in a file.

That is, an update history generated in a file included in a folder canbe regarded as one of update histories generated in the folder, anupdate history of a folder can include an update history of a file inthe folder, and a file badge value of a file can be added to a folderbadge value of a folder to which the file belongs.

When an update history is generated in a subfolder included in a folder,the update history is also included in details which need to be checkedby a folder participant for a task associated with the folder.Accordingly, the number of unchecked update histories with respect to asubfolder is also reflected in computation of a folder badge value. Thatis, an update history generated with respect to a file in a subfolder aswell as generation, modification and change of the subfolder are countedas update histories. In addition, the sum of update histories generatedwith respect to a subfolder can be at least a part of update historiesof a folder to which the subfolder belongs. That is, update histories ofa folder can include update histories of a subfolder included in thefolder.

Therefore, according to an embodiment of the present invention, a badgevalue of a folder can be computed by summing up i) the number ofunchecked update histories among update histories generated with respectto the folder (e.g., folder name changes, folder participant changes,etc.), ii) file badge values of files included in the folder and iii)badge values of subfolders included in the folder.

The file badge manager 350 can detect generation of update historiessuch as modifications and changes of a file by an arbitrary userterminal 120, calculate the number of unchecked update histories peruser among update histories generated with respect to the file as a filebadge value of the file, and generate a file badge corresponding to thebadge value. Accordingly, the file badge manager 350 can generate andupdate a file badge using one or more of update histories with respectto a specific file, time information about update histories,identification information about users who have updated the file,identification information of users who have accessed the file, andinformation about a time at which a specific user has accessed the file.

Here, files managed by the file badge manager 350 can include not onlygeneral user files but also folder memo pads, folder chat rooms and taskobjects associated with folders or files. Generation and management offile objects with respect thereto will be described later with referenceto FIG. 4 .

The file badge manager 350 can accumulate, store and manage updatehistories with respect to a specific file, time information about theupdate histories, identification information about users who haveupdated the file, identification information about users who haveaccessed the file, and information about a time at which a specific userhas accessed the file to generate a file modification history.

The folder badge manager 340 can also accumulate, store and manageupdate histories with respect to a file in a folder, time informationabout the update histories, identification information about users whohave updated the folder or the file, identification information aboutuser who have accessed the folder or the file, and information about atime at which a specific user has accessed the folder or the file, asdescribed above, to generate a folder modification history.

Here, the folder modification history and the file modification historycan be updated user-independently. A user-independent file modificationhistory per file includes file modification results of users withrespect to each file.

For example, when user A modifies file 1 in a folder, this affects allfolder users who participate in the folder and thus a foldermodification history per folder and a file modification history per fileare independently updated per user.

The folder badge manager 340 can accumulate update historiescorresponding to a period from the present to a specific time in thepast or a specific number of update histories in a folder modificationhistory per folder in a process of updating the folder modificationhistory per folder. For example, the folder badge manager 340 cansequentially accumulate folder update dates a, b, c and d generated withrespect to folder 1 in the folder modification history per folder. Inaddition, the folder badge manager 340 can store and manage updatehistories corresponding to a finite period from the current time or afinite number of update histories, for example, update historiesgenerated for the past one year or three months or up to 100 updatehistories, and reflect the update histories in a folder badge.

When a folder update is detected during a process of updating the foldermodification history per folder, the folder badge manager 340 canreflect user information of the corresponding user terminal 120 alongwith the folder update date in the folder modification history perfolder.

For example, whenever a folder update such as file addition, filemodification or folder modification occurs with respect to folder 1, thefolder badge manager 340 can accumulate and store the folder update dateand a user who generates the corresponding update history in the foldermodification history per folder.

That is, when the number of unchecked modifications other thanmodifications checked or read by a specific user among a total number ofmodifications of a specific file is counted, the result value ofcounting becomes a badge value of the file displayed to the user. Tothis end, according to an embodiment, it is possible to compare a filemodification time with a time at which the user has accessed the filemost recently and to set the number of modifications accumulated afterthe time at which the user has finally accessed the file to a file badgevalue.

The file badge manager 350 can provide a file badge per user per file tothe user terminal 120 such that the user terminal 120 visualizes a filebadge for each of at least one file included in the corresponding folderin a process of displaying a file list with respect to the correspondingfolder.

The file badge manager 350 detects reading of a file by the userterminal 120 and updates a badge with respect to the corresponding fileof the corresponding user. In an embodiment, the file badge manager 350can detect access of a user to a specific file, update a file accesstime per file, and update a file badge per file of the user.

For example, when the user terminal 120 of a user “Choi Jae-ho” opens ordownloads a file in the name of “filter quality assurance method” with afile badge of “3” among files in a folder, the file badge manager 350can update the file badge “3” of the file “filter quality assurancemethod” with respect to the user “Choi Jae-ho” to “0” and the folderbadge manager 340 can reduce the folder badge value of the folderincluding the file by 3.

The file badge manager 350 can accumulate a file badge per file for acorresponding folder and a corresponding subfolder of a correspondinguser on the basis of a file access time per file and a file modificationhistory per file of the user and reflect the file badge per file in afile badge accumulation count in the folder.

The update notification unit 360 can provide a notification fornotifying the user terminal 120 corresponding to each folder participantof generation of an update history with respect to a folder when anarbitrary user terminal 120 modifies or changes the folder or generates,modifies or changes a file or a subfolder in the folder and thus theupdate history with respect to the folder is newly generated.

More specifically, one of participants of a folder memo pad or a folderchat room associated with a folder may modify the folder memo pad orinput a new chat message to the folder chat room. Here, the updatenotification unit 360 can immediately provide a notification message forindicating that an update history with respect to the folder has beennewly generated separately from the operations of the folder badgemanager 340 and the file badge manager 350 to calculate a folder badgevalue and a file badge value and update a folder badge and a file badge.Here, the notification message can be transmitted to user terminals 120of folder participants other than the user who has generated the updatehistory.

For example, when a folder user authorized to access a specific foldermodifies a specific file in the folder, the update notification unit 360can provide details of a folder update history. That is, informationabout the modified file in the folder are provided to the user terminals120 of folder participants other than the user who has modified the fileof generation of the folder update history. Thus, the updatenotification unit 360 can immediately provide, to one or more userterminals 120, a notification message including one or more of i) thefact that an update history has been generated, ii) information about anupdated folder and iii) detailed information about the specific updatehistory (e.g., update type, updated file name, and the like) throughupdate notification.

The controller 370 can control the overall operation of the processor210 and control data flow between the folder access manager 310, thefolder list provider 320, the file list provider 330, the folder badgemanager 340, the file badge manager 350, and the update notificationunit 360.

The controller 370 may deliver data or signals between the folder accessmanager 310, the folder list provider 320 and the file list provider 330for calculation of badge values of the folder badge manager 340 and thefile badge manager 350 and activate or deactivate the folder accessmanager 310, the folder list provider 320 and the file list provider 330to control the operations thereof.

The controller 370 may provide unchecked update histories displayed onfolder badges or file badges or information about details of unprocessedtasks and priority among tasks while calculating and displaying badgevalues of folder badges and file badges. In this case, if there is atask object associated with a folder or a file, the controller 370 canuse information about a task processing period included in the taskobject.

The controller 370 can detect statistical information on updatehistories generated in a corresponding folder, all subfolders and filesin the folder, folder memo pads associated with the folder or files,folder chat rooms and task objects and reflect the statisticalinformation in an accumulated statistics count with respect to thecorresponding folder.

The controller 370 can perform a statistical operation on the basis ofat least one of all folder memo pads and folder chat rooms associatedwith the corresponding folder and subfolders of the correspondingfolder, task objects, the number of task objects generated through thefolder memo pads or the folder chat rooms, the number of processed taskobjects, task orderers and task handlers. Further, the controller 370can reflect the statistical operation result in the accumulatedstatistics count of the corresponding folder in a process of providing afolder list. The accumulated statistics count can be reflected incalculation of badge values of folder badges and displayed through thefolder badges.

Further, the controller 370 can detect a task object which satisfies aremind condition from task objects generated through folder memo pads orfolder chat rooms associated with a folder and substructures of thefolder on the basis of task progress states and deadlines at specificintervals and provide a reminder to the user terminal 120.

That is, the controller 370 can select only tasks having task progressstates and deadlines which satisfy predetermined conditions fromunprocessed/unchecked tasks accumulated in a corresponding folder usinginformation included in task objects to generate an urgent task list peruser. Here, the urgent task list can be detected for the folder and allsubfolders and files in the folder.

Accordingly, the controller 370 can notify present states of uncheckedupdate histories through a folder badge per folder and particularlyprovide an urgent task list indicating tasks having imminent processingtime limits to the user terminal 120. The user terminal 120 providedwith the urgent task list can visualize the urgent task list through areminder along with folder badges.

The controller 370 can search, filter or rearrange folders or content infolders on the basis of statistical information about unchecked updatehistories of folders at the request of the user terminal 120. Forexample, the controller 370 may arrange, at the request of the userterminal 120, folders or subfolders or files in a folder in descendingorder of the number of unchecked file updates or in order of imminentprocessing time limits per folder, in descending order of the number ofunchecked folder memo pad updates (i.e., in descending order of foldermemo badge values) or in descending order of the number of generatedtask objects or the number of task object updates (i.e., in descendingorder of task object badge values).

In addition, the controller 370 may provide a folder memo pad searchfunction of searching for a specific folder memo pad among folder memopads present in a folder or a substructure at the request of the userterminal 120.

Further, the controller 370 can accumulate statistical information abouttask objects associated with at least one file objects in a folder and acorresponding subfolder and reflect the accumulation result in a taskobject statics count in the folder. In an embodiment, the controller 370can detect statistical information about a task object associated with afile object present in a corresponding folder and include thestatistical information in an accumulated statics count.

For example, the controller 370 may perform a statistical operation onthe basis of at least one of the number of generated task objects, thenumber of processed task objects, a corresponding associated taskgenerator and task handler and reflect the statistical operation resultin the accumulated statistics count of the corresponding folder. Inaddition, the accumulated statistics count can be reflected in folderbadge computed during generation of a folder badge for the correspondingfolder.

FIG. 4 is a block diagram showing the file badge manager 350 of theprocessor in the folder management apparatus according to an embodimentof the present invention.

Files managed by a file object manager 410 with respect to generation offile badges can refer to general text files transmitted between userterminals 120 or general user files such as multimedia files like movingimages although they are not particularly limited.

The file object manager 410 can generate a user-independent filemodification history with respect to a file and add a modification time,a file modifier and modified content to the file modification historywhenever modification of the file is detected.

In one embodiment, the file object manager 410 can replicate filesbefore and after being modified to a file modification trackingcontainer of the file modification history to track modified content. Inaddition, the file object manager 410 can detect modification of thefile on the basis of the original file and reflect the detection resultin the file modification history.

Further, the file object manager 410 can generate a file badge per userindicating the number of unchecked updates per user on the basis of auser-independent file modification history with respect to a specificfile.

The file object manager 410 can immediately update an access time recordper user of the file modification history and a file badge per usercomputed therefrom whenever access to or modification of the specificfile is detected in real time. In addition, the file object manager 410can accumulate badge values of file badges generated for files, memopads or chat rooms associated with the specific file and reflect theaccumulated badge values in a file badge accumulation count of the file.

Here, when a badge value of a file badge exceeds a reference value, thecontroller 370 can recommend reading of the corresponding file to theuser terminal 120 corresponding to the file badge.

A folder memo pad manager 420 can provide a folder memo pad in a processof providing a folder list and a folder badge per user per folder. Here,a folder memo pad is a memo pad associated with a folder, can begenerated and accessed through the folder and supports functions ofrecording, sharing, modifying and tracking contents associated with thefolder.

A folder memo pad is shared by one or more folder users and may includea link connected to a specific file in a folder, and a memo of thefolder memo pad can be modified and tracked. An update history generatedwith respect to the folder memo pad may affect a badge value of thefolder memo pad and a badge value of the associated folder.

In an embodiment of the present invention, a folder memo pad can beincluded in a file list or separately displayed as a file. Since afolder memo pad is a file, information about modification or updatehistories with respect to the folder memo pad can be provided to theuser terminal 120 through a file badge for the folder memo pad. However,a file badge for a folder memo pad may be referred to as a folder memobadge for convenience of description and understanding.

In addition, the folder memo pad manager 420 checks the authority of theuser terminal 120 to access a folder memo pad associated with a folderand provides the folder memo pad. More specifically, the folder memo padmanager 420 can provide a folder memo pad which can be generated,modified or deleted by at least one folder user authorized to access thecorresponding folder and in which modification of memo content includedin a folder memo can be tracked.

In the case a folder memo pad is associated with a file, an updatehistory generated in the folder memo pad can be reflected in a filebadge value of the associated file and a folder badge value of a folderincluding the file. When a folder memo pad is generated in associationwith a folder, the controller 370 can reflect generation of the foldermemo pad in a folder modification history and update the folder badgevalue according to generation and update of the folder memo pad.

When a folder memo pad is generated in association with a specific filein a folder, generation of the folder memo pad can be reflected in afile modification history with respect to the file and a foldermodification history of the folder including the file, and a file badgeand a folder badge for the file and the folder can be updated accordingto generation and update of the folder memo pad.

The folder memo pad manager 420 can manage user information on a userwho has modified a folder memo pad along with the modification timewhenever an update history such as modification or change of the foldermemo pad is detected and provide user information on a user who hasmodified a memo in a process of providing tracked memo content such thatthe user terminal 120 can display memo content modified by differentusers in different colors, fonts or sizes.

In another embodiment, the folder memo pad manager 420 can store andmanage a file before being modified and a modified file when a foldermemo pad is modified by the user terminal 120 and manage files accordingto modification of files corresponding to a period from the present to aspecific time in the past or modification of a specific number of files.

Upon sensing or detecting the fact that the user terminal 120 has read afolder memo pad and an update history, the folder memo pad manager 420may track modified memo content by searching for a modified filegenerated after the most recent access time at which the usercorresponding to the user terminal 120 has accessed the folder memo padand comparing content between the modified file and a file before beingmodified immediately before the file modification.

A folder chat room manager 430 can provide a folder chat room in aprocess of providing a folder list and a folder badge per user perfolder. At least one folder user can share a folder chat room andparticipate therein. Here, a folder chat room is a chat room associatedwith a folder and that supports message conversations associated withthe folder between users. Accordingly, users can input message threadsfor conversations through the folder chat room and check message threadsinput by other users in real time.

In embodiments of the present invention, a folder chat room can beincluded in a file list or separately displayed as a kind of file. Sincea folder chat room is a file, information about modification or anupdate history with respect to the folder chat room can be provided tothe user terminal 120 through a file badge for the folder chat room.However, the file badge for the folder chat room may be referred to as afolder chat room badge for convenience of description and understanding.

Further, the folder chat room manager 430 can check the authority ofuser terminals 120 to access a folder chat room associated with a folderand provide the folder chat room only to a user terminal 120 confirmedto have the authority to access the folder chat room. That is, thefolder chat room manager 430 provides the chat room and message threadscorresponding to the chat room such that the chat room associated withthe folder can be substantiated and some or all of message threads inputthrough the user terminal 120 can be displayed on the user terminal uponconfirmation of the access authority of the user terminal 120.

More specifically, a folder chat room can be generated, deleted or readby at least one folder user authorized to access the correspondingfolder, and message threads can be added to the chat room.

The folder chat room manager 430 can generate a folder chat room after afolder is generated by a folder generator and determine chattingparticipants who will participate in the folder chat room through userselection and designation of the folder generator. Here, the chattingparticipants may be folder users of the folder. Entrance/exit ofchatting participants may affect increase/decrease in badge values of afolder chat room badge and a folder badge.

The folder chat room manager 430 can check the authority of the userterminal 120 to access folder chat rooms, select a folder chat roompermitted to be accessed by the user terminal and provide a folder chatroom list including information about the selected folder chat room andan access path to the selected folder chat room to the user terminal120.

The folder chat room manager 430 can detect an update history withrespect to a folder chat room and reflect the update history in a chatroom modification history. Here, the folder chat room manager 430 canrecognize addition of message threads to a folder chat room due tomessage input by other users, change in chatting participants of thefolder chat room, transmission of a file or generation of a task objectthrough the folder chat room, and the like as generation of updatehistories.

In addition, the folder chat room manager 430 can generate and update afile badge for the folder chat room, that is, a folder chat room badge,using the chat room modification history, user identificationinformation and information on the time at which the user terminalaccesses the folder chat room.

When a chat room is generated in association with a specific file in afolder, generation of the chat room can be reflected in the filemodification history with respect to the file as well as the foldercorresponding history with respect to the folder. In addition, thefolder chat room manager 430 can update the file badge and the folderbadge for the file and the folder including the file according togeneration and update of the chat room.

A task object manager 440 includes one or more of a task orderer, a taskhandler and a task instruction from an arbitrary user terminal 120 andcan receive task processing content through the task handler andgenerate a task object. Particularly, the task object manager 420 canreceive task processing content which can be fed back through a taskobject and add the task processing content to the task object.

More specifically, the task object manager 440 can receive a taskincluding information about at least one of task instruction created bya task orderer, a task handler, a task mark and a time limit from a userterminal 120 corresponding to the task orderer. Further, the task objectmanager 440 can encapsulate information about at least one of the taskorderer, task handler, task instruction, task processing content, taskmark and time limit of the task to generate a task object and associatethe task object with a folder, a file or a folder memo pad.

In addition, information necessary to generate a task object can bereceived through a chat room, a folder memo pad or the like. In such acase, the task object may be generated through the chat room or thefolder memo pad.

A task object can be stored in a folder or associated with a folder or afile in a folder as an independent task object message distinguishedfrom a text message or a multimedia message. Further, a task object maybe added to or associated with a folder memo pad or a task chat room.

Here, a task handler is a user designated by a corresponding taskorderer as a subject that processes a corresponding task and may be oneof a folder sharer and a folder participant. A task mark can include oneor both of a reserved evaluation score indicating an upper limit ofevaluation scores evaluated by the corresponding task orderer when thecorresponding task is completed and an evaluation score indicating anactually evaluated score. Accordingly, the task orderer can easily ordera task to a task handler through a folder and share task progress.

When a task object is generated through a folder memo pad or a task chatroom, the task orderer can share the task object through the folder memopad or the task chat room shared by participants of the folder memo pador the task chat room according to an embodiment of the presentinvention. In addition, the task orderer can easily order a task,receive a task progress report and evaluate the task by delivering thetask object to a task handler in the folder memo pad or the task chatroom.

A user can perform a task according to feedback through a task object,and the state of the task object can be updated as the task proceeds.The task object manager 440 can update the state of a task objectincluding a task progress state indicating a progress state per taskprocessing step and particularly update the task object on the basis offeedback from a task handler.

In one embodiment, the task object manager 440 can update a task objectin a folder memo pad by updating a predetermined task progress state ona task processing diagram which defines a task progress state perprocessing step on the basis of a request from one of a task orderer anda task handler and a response from the other.

Task progress through a task object, task object state change, taskobject state update and the like are recognized as generation of updatehistories with respect to the task object. Accordingly, the number ofupdate histories which have not been read by a user among updatehistories with respect to the task object is calculated as a badge valueof a task object badge. The task object manager 440 generates a taskobject badge on the basis of the task object badge value calculatedthrough the aforementioned process. The task object badge value can bereflected in the folder badge value of a folder associated with the taskobject.

For example, task progress states may include “new” indicating a statein which a task object has been newly generated, “in progress”indicating a state in which a task handler is processing a correspondingtask object, “done” indicating a state in which a task handler completesa task object and waits for interaction for completion of the task froma task orderer, and “confirm” indicating a state in which a task ordererhas checked a task object completed by a task handler.

The task object manager 440 can update a task progress state of a taskobject through a task object related response obtained from a responserelation between a target orderer and a target handler. Here, the taskobject related response corresponds to a response with respect to thetask object which can be replied by a user terminal 120 associated withthe task orderer or the task handler. In one embodiment, the task objectrelated response may include at least one of a task confirmationresponse, a task completion response and a task evaluation responseaccording to current task processing state of the corresponding taskobject.

For example, when the task object manager 440 updates a task progressstate of a specific task object from “new” into “in progress”, the filebadge value for the task object increases by 1. Here, the task objectmanager 440 can update the state of the task object by receiving a taskinteraction or task feedback from the user terminal 120 of the taskhandler with respect to the task object. The task object manager 440 canperform progress of the task object, receive evaluation regarding thetask object from a task orderer and assign the evaluation as a task markof the task object. Input of the task mark through a task object canalso be counted as one of update histories with respect to the taskobject.

The task object manager 440 can provide a remind message which isassociated with the task object and request completion of thecorresponding task progress state according to a specific repetitionstandard until the task progress state is completed to the user terminal120 associated with the corresponding task handler or the task ordereras a notification message. Generation of a new remind message ornotification message can also be counted as one of update histories withrespect to the task object.

The file badge manager 350 or the task object manager 440 can detect auser associated with a file badge which exceeds a reference badge amongfile badges for users with respect to a specific file object, notify theuser of update of the specific file object when the user logs in andprovides an access link to the file object to recommend checking ofupdate through the access link.

In one embodiment, when a file badge which exceeds a reference badgevalue (e.g., 10) is detected in a file modification history, the filebadge manager 350 or the task object manager 440 can provide the namesof other users who have modified the corresponding file after the usercorresponding to the detected file badge finally access the file, thefile badge and an access path for accessing the corresponding fileobject to the user terminal 120 of the user corresponding to thedetected file badge as a reading recommendation message for recommendingreading of the corresponding file.

FIG. 5 is a diagram showing a folder list and a list of files andsubfolders in a folder along with folder badges and file badgesaccording to an embodiment of the present invention.

FIG. 5 illustrates a folder list which can be displayed on a userterminal 120, a list of files in a folder and a list of subfolders in afile according to an embodiment of the present invention.

The folder list shown in FIG. 5 includes a folder X 510, a folder Y 512and a folder Z 514. A folder badge 520 of the folder X 510 has a folderbadge value of x, a folder badge 522 of the folder Y 512 has a folderbadge value of y and a folder badge 524 of the folder Z 514 has a folderbadge value of z.

In an embodiment described with reference to FIG. 5 , the folder X 510includes a file A 530, a file B 532, a file C 534, a first subfolder D536 and a first subfolder E 538. A file badge of the file A 530 has abadge value of a, a file badge of the file B 532 has a badge value of band a file badge of the file C 534 has a badge value of c. In addition,a first subfolder badge 546 of the first subfolder D 536 of the folder X510 has a badge value of d and a first subfolder badge 548 of the firstsubfolder E 538 of the folder X 510 has a badge value of e.

Here, the first subfolder D 536 includes a file F 550, a file G 552 anda second subfolder H 554. A file badge 560 of the file F 550 has a badgevalue of f, a file badge 562 of the file G 552 has a badge value of gand a second subfolder badge 564 of the second subfolder H 554 has abadge value of h.

Further, the folder X 510 is associated with a folder memo pad 570, afolder chat room 572 and a task object 574. Here, a file badge of thefolder memo pad 570, that is, a folder memo pad badge 580, has a badgevalue of i, a file badge of the folder chat room 572, that is, a folderchat room badge 582, has a badge value of j and a file badge of the taskobject 584, that is, a task object badge 584, has a badge value of k.

The folder badge value of the folder X 510 is x which means that thenumber of unchecked update histories associated with the folder X whichneed to be checked or read by a user when the user performs anassociated task using the folder X. That is, x can include the number ofunchecked update histories with respect to files, subfolders, foldermemo pads, folder chat rooms and task objects included in or associatedwith the folder X 510.

In addition, unchecked update histories of the folder X 510 may furtherinclude unchecked update histories with respect to the folder itselfamong update histories with respect to the folder itself in addition tounchecked update histories with respect to subfolders or files. Updatehistories with respect to the folder itself may refer to occurrence ofmodification and change of information about settings or attributes ofthe folder irrespective of files or subfolders included in the folder.

Accordingly, x can be calculated by summing up a, b, c, d, e, i, j and kand can be equal to or greater than the sum of a, b, c, d, e, i, j andk. x may be a value obtained by adding the number of unchecked updatehistories among update histories with respect to settings or attributesof the folder X 510 to the sum of a, b, c, d, e, i, j and k.

The first subfolder badge value d of the first subfolder D 536 can be avalue obtained by adding the folder badge value h of the secondsubfolder H 554 included in the first subfolder D 536 to the sum of thefile badge values f and g of the file F 550 and the file G 552 in thefirst subfolder D. Alternatively, d may be a value obtained by addingthe number of unchecked update histories generated for the firstsubfolder D 536 itself to the sum of f, g and h.

That is, when it is assumed that there is no update history with respectto the folder itself or update histories with respect to the folderitself are not added to the folder badge values, x and d can becalculated as follows.

x=a+b+c+d+e+i+j+k

d=f+g+h

Accordingly, when the user terminal 120 accesses the folder X 510, thefolder badge value x may not be automatically subtracted. However, thefolder badge value corresponding to the number of unchecked updatehistories among update histories with respect to the folder X (updatehistories generated with respect to the folder itself such as changes infolder settings or folder attributes such as the folder name andparticipants) can be subtracted only by access of the user terminal 120to the folder X 510.

When the user terminal 120 accesses the folder memo pad I 570 associatedwith the folder X 510 and checks all update histories with respect tothe folder memo pad, the folder badge value corresponding to i can besubtracted from x. When the user terminal 120 accesses the folder chatroom J 572 and checks all update histories of the chat room, the folderbadge value corresponding to j can be subtracted from x. When the userterminal 120 accesses the task object K 574 and checks all updatehistories with respect to the task object, the folder badge valuecorresponding to k can be subtracted from x. That is, if there is anunchecked update history with respect to the folder, the folder badgevalue may not be automatically subtracted before it is determined that auser actually checks or reads a corresponding part. However, a folderbadge value subtraction method may be set differently according toembodiments.

A folder badge value may be subtracted in the same manner with respectto a file or a subfolder. When the user terminal 120 accesses the file A530 and checks all unchecked update histories with respect to the file A530, a can be changed to 0 and the folder badge value x can be changedto x-a. This can be applied to the file B 532 and the file C 534 in thesame manner.

When the user terminal 120 accesses the first subfolder D 536, thefolder badge value corresponding to d can be immediately subtracted.However, according to an embodiment of the present invention, even afterthe user terminal 120 accesses the first subfolder D 536, the folderbadge value x of the folder X 510 can be subtracted by f and g only whenthe user terminal 120 accesses the file F 550 and the file G 552 to readunchecked update histories.

FIG. 6 is a diagram illustrating an embodiment of a procedure in whichthe folder badge manager of the present invention manages folder updatehistories using a sequential list vectorized in time series.

In one embodiment, the folder badge manager 340 can manage a time stamp,that is, access time record information of the user terminal 120, as atime variable parameter per user per folder for each folder in thefolder management system and reflect the time stamp in a folder badgeper user per folder. Here, the time stamp can include one or more of afolder generation time, a folder last modified time and a folder lastaccess time.

For example, the folder badge manager 340 can generate a folder badgeper user per folder defined through a time stamp per user per folder, asshown in FIG. 6(a), and update the folder badge per user per folderwhenever access to or modification of each folder is generated per user.

In addition, the folder badge manager 340 can compute and update afolder badge for each folder per user on the basis of a folder badge peruser per folder updated in real time, as shown in FIG. 6(b). If a user Ais a user of a user terminal 120 that requests access to a list offolders 1, 2 and 3, folder badges 0, 1 and 2 for the folders 1, 2 and 3can be provided to the user terminal 120.

When the authority of the user terminal 120 associated with the user Ato access the folder 1 is confirmed, the folder badge manager 340 candetect a generation time of 2017. 10. 21 12:08:51 and two modified times2017. 10. 22 09:43:20 and 2017. 10. 25 11:08:22 from folder modifiedhistories with respect to the folder 1, detect the last access time of2017. 10. 22 09:43:20 of the user A and count one-time modificationgenerated after the access time to compute the folder badge of the userA as 1. This means that, after the user A has last opened the folder,another user has updated the folder once.

FIG. 7 is a flowchart showing a folder management method according to anembodiment of the present invention.

A process in which the folder management apparatus 110 according to anembodiment of the present invention generates a folder badge will bedescribed with reference to FIG. 7 . Here, the folder badge may be asymbol indicating the number or folder update histories which have notbeen read by a user terminal when a file permitted to be accessed by theuser terminal is uploaded or updated to generate file update histories.In addition, in a specific folder, the number of folder update historieswhich have not been read by a user terminal may be a folder badge valuedisplayed through the folder badge of the folder.

Update histories with respect to a folder are generated (S610). Thefolder management apparatus 110 calculates the number of updatehistories generated with respect to the folder and calculates the numberof unchecked update histories per user (S620). Here, the number ofupdate histories generated with respect to the folder, that is, updatehistories with respect to changes in attributes or settings of thefolder, is calculated except update histories generated with respect tosubfolders or files included in the folder.

In addition, the folder management apparatus 110 determines whether thefolder includes content and whether an update history is generated inthe content included in the folder. First, the folder managementapparatus 110 determines whether the folder includes a file (S630).

When the folder includes a file, the folder management apparatus 110 cancalculate a badge value of a file badge for the file. The badge value ofthe file badge for the file can be calculated by counting the number ofupdate histories which are not checked by the user among the number ofaccumulated update histories generated with respect to the file. Thatis, the badge value of the file badge can be calculated by subtractingthe number of update histories determined to be read by the user byaccessing the file from the total number of accumulated update historiesgenerated with respect to the file (S640).

Then, the folder management apparatus 110 determines whether the folderincludes a subfolder (S650). When the folder includes a subfolder, thefolder management apparatus 110 calculates a badge value of a subfolderbadge by counting the number of unchecked update histories with respectto the subfolder (S660).

When the number of unchecked update histories generated with respect tothe folder, the badge value of the file badge for the file in thefolder, and the number of badge value of the subfolder badge for thesubfolder in the folder have been calculated, the folder managementapparatus 110 can calculate a badge value of a folder badge by summingup some or all of the numbers (S670).

The folder management apparatus 110 can generate the folder badge forthe folder using the calculated badge value of the folder badge (S680)and provide the folder badge to the user terminal such that the folderbadge can be displayed along with a folder list.

FIG. 8 is a flowchart showing a folder management method according toanother embodiment of the present invention.

When a user terminal 120 accesses the folder management system, thefolder management apparatus 110 detects the access of the user terminal120 (S710). The folder management apparatus 110 checks useridentification information and the range of the authority of the userterminal 120 and displays a folder list including folders accessible bythe user terminal 120 (S720).

In this process, the folder management apparatus 110 can verify whetherthe user terminal is authorized to access a specific folder first. Here,user terminal information and user identification information of a usercorresponding to the user terminal can be used. That is, the foldermanagement apparatus 110 can receive or acquire the user identificationinformation of the user corresponding to the user terminal 120 from theuser terminal and check whether the user terminal 120 has the authorityto access the folder management system and whether the user terminal 120has the authority to access each folder in the system. In addition, thefolder management apparatus 110 can display a folder list includingfolders confirmed to be accessible by the user terminal 120.

Here, when the folder list is displayed, folder badges of folders canalso be displayed. The folder management apparatus 110 may select afolder recommended to be checked first according to priority to the userterminal 120 and provide information about a folder for which urgentprocessing or preferential checking is recommended.

For example, a folder for which urgent processing or preferentialchecking is recommended may be selected on the basis of a folder havinga folder badge exceeding a predetermined reference value, a folderincluding a task object having an imminent processing time limit checkedthrough information about task processing time limits included in taskobjects, and a folder in which the number of task objects or folder memopads generated in association with the folder exceeds a predeterminedreference value.

Thereafter, the user terminal 120 accesses one of the folders includedin the displayed folder list (S730).

First, the folder management apparatus 110 determines whether the folderbadge value will be subtracted only through access of the user terminal120 to the folder. That is, the folder management apparatus 110determines whether update histories generated with respect to the folderinclude an unchecked update history (S740). Although unchecked updatehistories accumulated with respect to a file or a subfolder included inthe folder are not read only by accessing the folder, an uncheckedupdate history due to change in settings or attributes of the folderbefore access of the user terminal 120 can be considered to be read whenthe user terminal 120 accesses the folder.

Accordingly, the number of unchecked update histories accumulated beforethe user terminal 120 accesses the folder among unchecked updatehistories with respect to the folder can be subtracted from the folderbadge value when the user terminal 120 accesses the folder (S750).

Thereafter, the user terminal 120 can access a subfolder or a file inthe folder (S760). The folder management apparatus 110 determineswhether there are unchecked update histories with respect to thesubfolder or the file (S770). If there are unchecked update historieswith respect to the file, which have been accumulated before the userterminal 120 accesses the file, the user terminal accesses the file andreads the unchecked update histories, and the number of unchecked updatehistories can be subtracted from the folder badge value. If the userterminal 120 accesses the subfolder, when there are accumulatedunchecked update histories with respect to the subfolder before the userterminal 120 accesses the subfolder and the user terminal 120 accessesthe subfolder to read the unchecked update histories, the number ofunchecked update histories read by the user terminal 120 can besubtracted from the folder badge value (S780).

Through the above-described process, when the user terminal 120 accessesthe folder, the subfolder and the file to read unchecked updatehistories, the folder management apparatus 110 can calculate a finalfolder badge value according to access and reading of the user terminal120 by subtracting the total number of read unchecked update historiesfrom the folder badge value (S790). Then, the folder managementapparatus can update the folder badge of the folder according to thecalculated final folder badge value.

When unchecked update histories are accumulated after access of the userterminal 120, the folder badge value increases by the number ofadditionally accumulated unchecked update histories. That is, the foldermanagement apparatus 110 can detect update histories with respect to afolder, reflect the update histories in a folder modification history,generate a folder badge using the folder modification history in whichthe update histories have been reflected, user identificationinformation and information on the last access time of the user terminal120 for the folder and continuously update the folder badge.

Although preferred embodiments of the present application have beendescribed above, those skilled in the art will appreciate that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the invention described inthe appended claims.

The folder management apparatus and method according to an embodiment ofthe present invention can provide intuitive notification to a user withrespect to folder update of other users using the concept of the folderbadge per user per folder.

In addition, it is possible to provide information updated in real timeto users and provide convenience in folder management for each user byincreasing or decreasing a file badge value or a folder badge valueaccording to whether an event has been checked per user.

What is claimed is:
 1. An apparatus for managing a folder, the apparatuscomprising: a memory; and a processor electrically connected to thememory, wherein the processor is configured to detect access of a userterminal, provide a folder list for folders or a file list for files ina folder, and when an access authority of the user terminal to aspecific folder is confirmed, provide a folder memo pad including afolder memo in a process of providing a folder list and a folder badgeassociated with the specific folder, wherein the folder memo is realizedas a memo pad associated with the specific folder in the user terminaland for which modification is tracked.
 2. The apparatus of claim 1,wherein the processor provides a modification history or an updatehistory of the folder memo pad to the user terminal through a file badgeof the folder memo pad.
 3. The apparatus of claim 1, wherein, when thefolder memo pad is generated in association with the specific folder,the processor reflects the generation of the folder memo pad in a foldermodification history and updates a folder badge value of the specificfolder in response to the generation and update of the folder memo pad.4. The apparatus of claim 1, wherein, in the case of a folder memo padassociated with the specific file, the processor reflects the generationof the folder memo pad in a file modification history and reflects anupdate history generated in the folder memo pad in a file badge value ofthe specific file.
 5. The apparatus of claim 1, wherein, when an updatehistory such as modification or change of the folder memo pad isdetected, the processor manages user information on a user who hasperformed the corresponding modification along with the correspondingmodification time.
 6. The apparatus of claim 5, wherein the processorprovides user information on a user who has modified the correspondingmemo together in a process of providing tracked memo content of thefolder memo pad and displays memo content modified by different users indifferent colors, fonts, or sizes.
 7. The apparatus of claim 1, wherein,upon sensing or detecting the fact that the user terminal has read thefolder memo pad and the update history, the processor searches for amodified file generated after the most recent access time at which thecorresponding user has accessed the corresponding folder memo pad andtracks modified memo content by comparing content between thecorresponding modified file and a file before being modified immediatelybefore the file modification.
 8. The apparatus of claim 1, wherein, in aprocess of providing the folder list, the processor performs astatistical operation on the basis of at least one of all folder memopads and folder chat rooms associated with the respective folders andsubfolders of the corresponding folders, task objects, the number oftask objects generated through the folder memo pads or the folder chatrooms, the number of processed task objects, task orderers, and taskhandlers, and reflects the statistical operation in an accumulatedstatistics count of the corresponding folders.
 9. The apparatus of claim1, wherein the processor provides a folder memo pad search function ofsearching for a specific folder memo pad among folder memo pads presentin a folder or a substructure at a request of the user terminal.
 10. Afolder management method performed by a folder management apparatusincluding a memory and a processor electrically connected to the memory,the method comprising: detecting access of a user terminal, providing afolder list of folders or a file list of files within a folder, and whenan access authority of the user terminal to a specific folder isconfirmed, providing a folder memo pad including a folder memo in aprocess of providing a folder list and a folder badge associated withthe specific folder, wherein the folder memo is realized as a memo padassociated with the specific folder in the user terminal and for whichmodification is tracked.